SEO blogs targetting AI by atharvadeosthale · Pull Request #2908 · appwrite/website

atharvadeosthale · 2026-04-22T20:56:11Z

No description provided.

greptile-apps · 2026-04-22T20:58:45Z

Greptile Summary

Adds 15 SEO-focused blog posts targeting AI/vibe-coding keywords, covering comparison pieces (Appwrite vs Supabase, Firebase, Neon, Cloudflare, Convex, Replit), educational posts on AI backends, and Lovable pairing guides — all marked unlisted: true and accompanied by cover images and cache entries.

The posts are well-structured with mostly consistent doc links. Three minor cross-post consistency issues were found: two incorrect link targets in the Firebase comparison post, a differing OAuth provider count in the Replit post, and a conflicting Neon self-hosting value in the Supabase alternatives comparison table.

Confidence Score: 5/5

Safe to merge; all findings are minor content consistency issues with no runtime or structural impact.

All 29 files are static content (Markdoc blog posts and images). The three flagged issues are P2 style/consistency concerns — a wrong link destination, a differing number in an approximate OAuth provider count, and a conflicting self-hosting value across tables. None affect site functionality or cause 404s.

src/routes/blog/post/appwrite-vs-firebase-ai-development/+page.markdoc (wrong link targets on line 21), src/routes/blog/post/appwrite-vs-replit-agent-backend/+page.markdoc (provider count), src/routes/blog/post/supabase-alternatives-lovable-projects/+page.markdoc (Neon self-host value).

Important Files Changed

Filename	Overview
src/routes/blog/post/appwrite-vs-firebase-ai-development/+page.markdoc	New SEO comparison post; Agent Skills and Assistant links on line 21 point to the AI hub instead of their specific doc pages.
src/routes/blog/post/appwrite-vs-replit-agent-backend/+page.markdoc	New comparison post; OAuth provider count (~40) inconsistent with ~44 used in the rest of this PR.
src/routes/blog/post/supabase-alternatives-lovable-projects/+page.markdoc	New comparison overview post; Neon self-host column shows No but conflicts with the more nuanced description in the open-source post.
src/routes/blog/post/agent-native-backend-platforms/+page.markdoc	New overview post on agent-native backends; content and internal links are correct.
src/routes/blog/post/appwrite-vs-cloudflare-stateful-ai-agents/+page.markdoc	New Cloudflare comparison post; content, links, and frontmatter look correct.
src/routes/blog/post/appwrite-vs-convex-ai-agents/+page.markdoc	New Convex comparison post; content and links are consistent with other posts in the PR.
src/routes/blog/post/appwrite-vs-neon-ai-backends/+page.markdoc	New Neon comparison post; content and links look correct.
src/routes/blog/post/appwrite-vs-supabase-ai-apps/+page.markdoc	New Supabase comparison post; all doc links use correct paths.
src/routes/blog/post/backend-checklist-vibe-coded-apps/+page.markdoc	New pre-launch checklist post for vibe-coded apps; content and structure look good.
src/routes/blog/post/best-backend-for-lovable-apps/+page.markdoc	New decision guide post for Lovable backends; links and content are consistent.
src/routes/blog/post/lovable-appwrite-backend-pairing/+page.markdoc	New pairing guide post; content and doc links are accurate.
src/routes/blog/post/open-source-backend-for-ai-apps/+page.markdoc	New open-source comparison post; Neon self-hosting nuance expressed more accurately here than in the supabase-alternatives post.
src/routes/blog/post/what-is-an-ai-backend/+page.markdoc	New definitional/educational post; all doc links use correct paths including /docs/apis/realtime.
src/routes/blog/post/why-ai-generated-apps-need-backend/+page.markdoc	New educational post explaining backend necessity for AI-generated apps; content is clean.
.optimize-cache.json	Adds cache entries for 15 new cover images, all matching the new blog post directories.

_{Reviews (5): Last reviewed commit: "fix broken /docs/products/realtime links..." | Re-trigger Greptile}

TorstenDittmann · 2026-04-30T18:44:31Z

+
+Picking a backend for an app that an AI coding agent will help build is a decision with a long half-life. The agent spends most of its context budget reasoning about identity, data, files, server-side code, and hosting, so the platform underneath has to give it clear primitives, a stable API, and an MCP surface the model can use directly. Appwrite vs Firebase AI is the comparison teams run when they weigh an open-source, self-hostable backend against Google's AI assistance ecosystem.
+
+This article looks at Appwrite as a Firebase alternative for AI apps, focused on open-source flexibility, MCP coverage, SDK breadth, Databases with tables and rows, Functions, Sites, and self-hosting, against Firebase's Gemini in Firebase, Firebase MCP server, Gemini CLI extension, and agent skills.


A section later covers this, talks about variety of SDKs

TorstenDittmann · 2026-04-30T18:47:08Z

+
+| Capability | Appwrite | Firebase |
+| --- | --- | --- |
+| Auth | Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers | Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, Twitter, GitHub, and others; SAML and OIDC through Identity Platform upgrade |


Twitter = X

Suggested change

| Auth | Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers | Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, Twitter, GitHub, and others; SAML and OIDC through Identity Platform upgrade |

| Auth | Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers | Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, X, GitHub, and others; SAML and OIDC through Identity Platform upgrade |

TorstenDittmann · 2026-04-30T18:53:04Z

+
+Choose Appwrite if:
+
+- You want one open-source platform covering Auth, tables, Storage, Functions, Realtime, Messaging, and hosting for your AI-generated frontend, all reachable through an MCP server.


Tables is lower case

adityaoberai · 2026-04-23T19:07:53Z

+
+Put together, these shifts mean backend platforms are being evaluated against a new checklist: does an agent already understand your product, can it act on it safely, and does it stay current?
+
+# How the leading platforms are positioning


Appwrite not being in the section of leading platforms can send the wrong message forward (even though the next section fits us in here)

Let's shift the Appwrite section above this and instead of titling it as "leading platforms", we can say "alternative platforms"

adityaoberai · 2026-04-30T21:49:05Z

+
+| Capability | Appwrite | Firebase |
+| --- | --- | --- |
+| Auth | Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers | Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, Twitter, GitHub, and others; SAML and OIDC through Identity Platform upgrade |


Suggested change

| Auth | Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers | Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, Twitter, GitHub, and others; SAML and OIDC through Identity Platform upgrade |

| Auth | Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers | Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, X, GitHub, and others; SAML and OIDC through Identity Platform upgrade |

adityaoberai · 2026-04-30T21:49:27Z

+
+Appwrite [Auth](/docs/products/auth) covers email and password, magic URL, email OTP, phone, anonymous sessions, JWTs, custom tokens for existing auth systems, and OAuth2 across roughly 44 providers. Teams, labels, and row-level permissions give AI-generated rules a predictable place to live.
+
+[Firebase Authentication](https://firebase.google.com/docs/auth) supports email and password, phone, anonymous, and popular federated providers including Google, Apple, Facebook, Twitter, and GitHub, with drop-in UI through FirebaseUI. Multi-factor authentication, SAML, OpenID Connect providers, and multi-tenancy require an upgrade to Firebase Authentication with Identity Platform. That upgrade is a normal path for larger apps; it is also an extra tier an agent has to know about when it generates enterprise login flows.


Suggested change

[Firebase Authentication](https://firebase.google.com/docs/auth) supports email and password, phone, anonymous, and popular federated providers including Google, Apple, Facebook, Twitter, and GitHub, with drop-in UI through FirebaseUI. Multi-factor authentication, SAML, OpenID Connect providers, and multi-tenancy require an upgrade to Firebase Authentication with Identity Platform. That upgrade is a normal path for larger apps; it is also an extra tier an agent has to know about when it generates enterprise login flows.

[Firebase Authentication](https://firebase.google.com/docs/auth) supports email and password, phone, anonymous, and popular federated providers including Google, Apple, Facebook, X, and GitHub, with drop-in UI through FirebaseUI. Multi-factor authentication, SAML, OpenID Connect providers, and multi-tenancy require an upgrade to Firebase Authentication with Identity Platform. That upgrade is a normal path for larger apps; it is also an extra tier an agent has to know about when it generates enterprise login flows.

adityaoberai · 2026-04-30T21:58:31Z

+
+Auth is where most vibe-coded apps leak first. The UI looks finished and the signup flow works on the demo account, so the assumption is that the rest will follow.
+
+- [ ] Decide which identity methods you support (email and password, magic URL, email OTP, OAuth, phone OTP, anonymous) and remove every flow you do not.


I don't think we need - [ ] style checkboxes in the UI

A simple list will do

adityaoberai · 2026-04-30T21:58:54Z

+
+## 1. Authentication that covers your sign-in flows
+
+A lovable backend needs more than a demo sign-in screen. Look for:


Suggested change

A lovable backend needs more than a demo sign-in screen. Look for:

A Lovable backend needs more than a demo sign-in screen. Look for:

adityaoberai · 2026-04-30T22:00:07Z

+In practice, a Lovable team using Appwrite as their backend works like this: build the UI in Lovable, connect the Appwrite docs MCP server inside Lovable's personal connectors so the chat has accurate Appwrite context, and wire the generated frontend to Appwrite through the web SDK. Heavier work such as schema changes, server-side logic, and deploys happen through the Appwrite console, SDKs, CLI, or other AI tools configured with the Appwrite MCP servers.
+
+# Comparing backend shapes at a glance
+


This blog doesn't need a comparison, we just need to talk about how Appwrite solves these problems

adityaoberai · 2026-04-30T22:02:11Z

+
+Not every Lovable project needs a broad backend platform. Sometimes the right answer is "replace Supabase with a different single-purpose backend," and sometimes it is "use a different integration inside Lovable." The options below are worth considering.
+
+## Lovable Cloud


Not sure if it makes sense to include this

# Conflicts: # .optimize-cache.json

… comparisons

ai seo blogs first batch

dd8f3e3

atharvadeosthale marked this pull request as draft April 22, 2026 20:56

TorstenDittmann reviewed Apr 30, 2026

View reviewed changes

adityaoberai marked this pull request as ready for review April 30, 2026 21:45

adityaoberai requested changes Apr 30, 2026

View reviewed changes

atharvadeosthale added 3 commits May 1, 2026 21:16

Merge remote-tracking branch 'origin/main' into atharva/ai-seo-blogs

322893a

# Conflicts: # .optimize-cache.json

address PR review comments: stretch dates, add plugins/skills, soften…

c2fe24d

… comparisons

cycle blog authors between aditya, atharva, aishwari

38e7cc9

atharvadeosthale requested a review from adityaoberai May 1, 2026 15:55

greptile-apps Bot reviewed May 1, 2026

View reviewed changes

Comment thread src/routes/blog/post/what-is-an-ai-backend/+page.markdoc Outdated

fix broken /docs/products/realtime links to /docs/apis/realtime

68d8306


		Picking a backend for an app that an AI coding agent will help build is a decision with a long half-life. The agent spends most of its context budget reasoning about identity, data, files, server-side code, and hosting, so the platform underneath has to give it clear primitives, a stable API, and an MCP surface the model can use directly. Appwrite vs Firebase AI is the comparison teams run when they weigh an open-source, self-hostable backend against Google's AI assistance ecosystem.

		This article looks at Appwrite as a Firebase alternative for AI apps, focused on open-source flexibility, MCP coverage, SDK breadth, Databases with tables and rows, Functions, Sites, and self-hosting, against Firebase's Gemini in Firebase, Firebase MCP server, Gemini CLI extension, and agent skills.

	\| Auth \| Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers \| Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, Twitter, GitHub, and others; SAML and OIDC through Identity Platform upgrade \|
	\| Auth \| Email and password, magic URL, email OTP, phone, anonymous, JWT, custom tokens, OAuth2 with roughly 44 providers \| Email and password, phone, anonymous, OAuth with Google, Apple, Facebook, X, GitHub, and others; SAML and OIDC through Identity Platform upgrade \|


		Choose Appwrite if:

		- You want one open-source platform covering Auth, tables, Storage, Functions, Realtime, Messaging, and hosting for your AI-generated frontend, all reachable through an MCP server.


		Put together, these shifts mean backend platforms are being evaluated against a new checklist: does an agent already understand your product, can it act on it safely, and does it stay current?

		# How the leading platforms are positioning


		Appwrite [Auth](/docs/products/auth) covers email and password, magic URL, email OTP, phone, anonymous sessions, JWTs, custom tokens for existing auth systems, and OAuth2 across roughly 44 providers. Teams, labels, and row-level permissions give AI-generated rules a predictable place to live.

		[Firebase Authentication](https://firebase.google.com/docs/auth) supports email and password, phone, anonymous, and popular federated providers including Google, Apple, Facebook, Twitter, and GitHub, with drop-in UI through FirebaseUI. Multi-factor authentication, SAML, OpenID Connect providers, and multi-tenancy require an upgrade to Firebase Authentication with Identity Platform. That upgrade is a normal path for larger apps; it is also an extra tier an agent has to know about when it generates enterprise login flows.


		Auth is where most vibe-coded apps leak first. The UI looks finished and the signup flow works on the demo account, so the assumption is that the rest will follow.

		- [ ] Decide which identity methods you support (email and password, magic URL, email OTP, OAuth, phone OTP, anonymous) and remove every flow you do not.


		## 1. Authentication that covers your sign-in flows

		A lovable backend needs more than a demo sign-in screen. Look for:

		In practice, a Lovable team using Appwrite as their backend works like this: build the UI in Lovable, connect the Appwrite docs MCP server inside Lovable's personal connectors so the chat has accurate Appwrite context, and wire the generated frontend to Appwrite through the web SDK. Heavier work such as schema changes, server-side logic, and deploys happen through the Appwrite console, SDKs, CLI, or other AI tools configured with the Appwrite MCP servers.

		# Comparing backend shapes at a glance


		Not every Lovable project needs a broad backend platform. Sometimes the right answer is "replace Supabase with a different single-purpose backend," and sometimes it is "use a different integration inside Lovable." The options below are worth considering.

		## Lovable Cloud

Conversation

atharvadeosthale commented Apr 22, 2026

Uh oh!

greptile-apps Bot commented Apr 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 5/5

Important Files Changed

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

greptile-apps Bot commented Apr 22, 2026 •

edited

Loading